Release notes for 26/05#267
Conversation
✅ Deploy Preview for absmartly-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
WalkthroughThis pull request adds comprehensive documentation for ABsmartly's May 2026 product updates. It introduces a new Activity per Period metric type with standalone documentation, publishes release notes covering multiple features including Metric Changelog (audit trail with field-level diffs), improved metrics discoverability, keyboard navigation in Event Details, and early-beta Custom Assignments for the JavaScript SDK. The PR updates existing feature guidance to clarify the limited beta status and enablement requirements for Custom Assignments, and expands the glossary with a Warehouse-native entry describing warehouse-native deployment architecture. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
docs/platform-release-notes/2026/05.mdx (1)
88-88: ⚡ Quick winAdd missing final newline.
The file should end with a newline character for POSIX compliance and better Git diffs.
📝 Proposed fix
We're always happy to help, so reach out if you have any questions or want to explore how to make the most of these new capabilities. +🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/platform-release-notes/2026/05.mdx` at line 88, The MDX release notes file is missing a final newline character at EOF; open the 05.mdx document and add a single trailing newline character at the end of the file so it ends with a newline (POSIX-compliant), then save and commit the change.docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx (1)
58-58: ⚡ Quick winAdd missing final newline.
The file should end with a newline character for POSIX compliance and better Git diffs.
📝 Proposed fix
- Ideal for experiments aimed at **engagement, habit formation, or retention frequency** — onboarding flows, notifications, recommendation systems, or loyalty mechanics. +🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx` at line 58, The file is missing a trailing newline at EOF; open the "Activity per Period" metric page source and ensure the document ends with a single POSIX newline character (add an empty line after the last content) so the file terminates with '\n' to satisfy POSIX/Git expectations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/platform-release-notes/2026/05.mdx`:
- Line 23: The list item containing "**Identity**, **Details**, **Definition**
**Goal**" is missing proper punctuation between "Definition" and "Goal"; update
the text in that list entry so the section names are unambiguous—either insert a
comma to make "**Definition**, **Goal**" if they are separate sections, or
collapse them into a single section name like "**Definition Goal**" (or adjust
bolding to reflect the intended single-section string); edit the same list line
to ensure consistent comma separation for all items such as "**Identity**,
**Details**, **Definition**, **Goal**" if there are four sections.
---
Nitpick comments:
In `@docs/platform-release-notes/2026/05.mdx`:
- Line 88: The MDX release notes file is missing a final newline character at
EOF; open the 05.mdx document and add a single trailing newline character at the
end of the file so it ends with a newline (POSIX-compliant), then save and
commit the change.
In
`@docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx`:
- Line 58: The file is missing a trailing newline at EOF; open the "Activity per
Period" metric page source and ensure the document ends with a single POSIX
newline character (add an empty line after the last content) so the file
terminates with '\n' to satisfy POSIX/Git expectations.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 8cb1b4ab-487d-41e8-8d8e-f89a7dcd07a5
⛔ Files ignored due to path filters (1)
static/img/release-notes/metric-changelog.pngis excluded by!**/*.png
📒 Files selected for processing (4)
docs/glossary.mdxdocs/platform-release-notes/2026/05.mdxdocs/web-console-docs/experiments/creating-an-experiment.mdxdocs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx
| - **When** it happened (relative time, with the exact timestamp on hover) | ||
| - **Which metric version** the change produced | ||
| - **A short summary** of the change (e.g. _Changed owners_, _Added metadata_) | ||
| - **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition** **Goal**, with clear add/remove indicators |
There was a problem hiding this comment.
Clarify the section list formatting.
The list of collapsible sections appears to be missing proper punctuation or formatting between "Definition" and "Goal". This should likely be either:
- "Definition, Goal" (if these are separate sections), or
- Verify if "Definition Goal" is a single section name
📝 Proposed fix (if separate sections)
-- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition** **Goal**, with clear add/remove indicators
+- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition**, **Goal**, with clear add/remove indicators📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition** **Goal**, with clear add/remove indicators | |
| - **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition**, **Goal**, with clear add/remove indicators |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/platform-release-notes/2026/05.mdx` at line 23, The list item containing
"**Identity**, **Details**, **Definition** **Goal**" is missing proper
punctuation between "Definition" and "Goal"; update the text in that list entry
so the section names are unambiguous—either insert a comma to make
"**Definition**, **Goal**" if they are separate sections, or collapse them into
a single section name like "**Definition Goal**" (or adjust bolding to reflect
the intended single-section string); edit the same list line to ensure
consistent comma separation for all items such as "**Identity**, **Details**,
**Definition**, **Goal**" if there are four sections.
Demote Custom Assignments (Exclusion Rules) from H2 to H3 so it lives inside the Audiences section instead of being a peer to it.
Replace with the latest version showing teams/tags/category/applications diff.
Summary by CodeRabbit
Release Notes
New Features
Documentation